fix(test) fix cron cycles #8322
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
skrdgraph
requested review from
akon-dey,
gcxml,
darkn3rd and
meghalims
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
we have switched to self-hosted runners, and we are spending $'s for our runners. Our tests are now stable, and we ideal need 1-runner during the night for scheduled runs. And if we do get PRs etc. on our
mainbranch - it would still be able to run those tests. We should not need 2 runners during the 12hr off-work window.Solution
Adjust the schedule in such a way that
unit test runis followed byload test runsequentially. This will keep the resource busy for ~20mins. And we will need only 1 runner for the night.